Segfault when enabling monitor mode with TL-WN722N v2
I bought a TL-WN722N for monitor mode sniffing under Ubuntu since I saw it on a list of supported devices (the internal WiFi on this laptop is not supported) but it crashes Wireshark with a segfault when I click on the monitor mode checkbox.
I've tried running airmon-ng as how-tos have described but it shows the PHY as 'null' for the interface.
Has anyone else had any luck with this adapter in monitor mode? Can someone recommend an adapter that's known to work reliably? All I need to do is capture small amounts of traffic off the air to diagnose a problem with an embedded WiFi device that sometimes doesn't get DHCP (as well as a few other problems), and last time I did any real sysadmin work on Linux, WiFi was still barely even supported - I'm a little out of date and short on hours in the day to relearn it all.
I'm on the verge of trying to find someone with a complete configured and working laptop to sell.
Thanks,
Scott
Do you have a stack trace for the crash? It shouldn't crash, even if it fails for some reason.
We can’t really recommend an adapter that will work if we don’t know what you need. The v1 adapter is 802.11 bgn 1x1:1; so if you, for instance, need to capture 802.11ac with LDPC and 2 SS, this won’t work.
How about something like this?
https://www.amazon.com/Automation-sim...11?ie=UTF8&qid=1543781061&sr=8-1&keywords=Omnipeek
I've got a core dump. How do I get a stack trace? gdb says 'no stack'. I ran Wireshark with valgrind -v and it didn't crash that way - just refreshed the interface list when I tried to enable monitor mode. Valgrind did give a bunch of messages. Tried again without valgrind and it still segfaults.
I only need to capture 802.11 b/g/n from an embedded WiFi module for troubleshooting purposes. It has a peak throughput of about 2 Mbps. Basically this comes down to proving to Silicon Labs that their module is misbehaving - finding out why DHCP consistently fails on some APs, showing that dropped connections aren't caused by the AP, that sort of thing.
I'm an embedded developer, 15 years out of practice on *nix systems administration, so please be gentle!
What was the command you ran GDB with, and what command did you give to gdb to get the stack trace (probably
backtrace
,bt
, orwhere
)?Have a look at netgear wnda4100; that is an ralink chipset that I have had good luck with. Amazon has some refurbished ones. Most ralink chipsets will work.